Standardize Thread Naming - Prioritization Fee Cache #30890
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@taozhu-chicago sorry for nitting this old thread name haha. Feel free to suggest a different (<=15 character) name 😄 |
tao-stones
approved these changes
Mar 24, 2023
Codecov Report
@@ Coverage Diff @@
## master #30890 +/- ##
=========================================
- Coverage 81.5% 81.5% -0.1%
=========================================
Files 726 726
Lines 204809 204914 +105
=========================================
+ Hits 167027 167055 +28
- Misses 37782 37859 +77 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
In #27237 @mvines has tried to standardize solana-controlled thread names. This thread was introduced around the same time, and so it has snuck through.
Summary of Changes
Shorten thread name to 15 characters.
Fixes #